Skip to content

[Snyk] Security upgrade org.json4s:json4s-jackson_2.11 from 3.5.3 to 4.0.0#186

Open
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-716c2a52aeac0eced577c8986e888123
Open

[Snyk] Security upgrade org.json4s:json4s-jackson_2.11 from 3.5.3 to 4.0.0#186
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-716c2a52aeac0eced577c8986e888123

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io bot commented Apr 5, 2026

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • samples/client/petstore/akka-scala/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
high severity Allocation of Resources Without Limits or Throttling
SNYK-JAVA-COMFASTERXMLJACKSONCORE-15907551
  125   org.json4s:json4s-jackson_2.11:
3.5.3 -> 4.0.0
Major version upgrade No Path Found No Known Exploit

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

@snyk-io
Copy link
Copy Markdown
Author

snyk-io bot commented Apr 5, 2026

Merge Risk: High

This is a major version upgrade from 3.5.3 to 4.0.0 that introduces significant breaking changes.

Key Changes:

  • Binary Incompatibility: The 4.0.0 release is not binary compatible with the 3.x series. Downstream projects have explicitly noted this breakage.
  • Significant API Discrepancies: There are major differences in API behavior between the 3.x and 4.x versions. The changes were substantial enough that Databricks noted significant discrepancies and chose to downgrade from json4s 4.x back to a 3.x version in their runtime to maintain compatibility.
  • Potential Core API Changes: Discussions leading up to this major version indicated potential redesigns of core data structures, such as changing JObject from using a List to a Map and altering the collection type for JArray. Such changes would require significant code refactoring for anyone interacting directly with the JSON AST.

Recommendation: Due to the high likelihood of breaking API and binary compatibility changes, this upgrade requires a thorough code review and refactoring effort. Developers should carefully test all JSON parsing, serialization, and AST manipulation logic.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@snyk-io
Copy link
Copy Markdown
Author

snyk-io bot commented Apr 5, 2026

Snyk checks have failed. 1 issues have been found so far.

Status Scan Engine Critical High Medium Low Total (1)
Open Source Security 0 0 1 0 1 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants